This PR updates the notification server to use IDs rather than timestamps when determining which notifications to process. This relies on the fact that local IDs are always incrementing. This should solve at least two problems with missing notifications.

• Notifications may be missing due to a race condition, where a notification arrives after we have done the processing but before we have updated the timestamp.
• Notifications may be missing due to federation issues, where a notification with an old publication date does not get federated until sometime later (fortunately, in this case, the ID is still incremented on the local instance).

Eventually we should probably make a similar change in Thunder for local notifications, but I think it's less of an issue (seems to be more related to the federation case than the race condition case).